test(load): cover missing extension creation from CFE - #51
Conversation
- add a CLI regression for loading a missing CFE extension\n- document Designer-only creation boundaries
- verify the missing-extension comparison precedes load and DB update
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Closes #18.
Documents and regression-tests the existing Designer artifact workflow that creates a missing extension via
load --path <artifact.cfe> --mode load --extension <name>.The test verifies
CompareCfgprobe precedesLoadCfg -Extension, which precedesUpdateDBCfg -Extension; it asserts typed JSON result fields for missing-extension creation.Scope intentionally excludes source-set build creation, schema changes, and MCP API changes.
Verification: cargo test --test cli_load (9 passed); cargo fmt --all -- --check; cargo check; git diff --check.